clX The Clause Cross Referencer by Andrew McBurnie version 2.2, March, 1993. copyright 1993, Andrew McBurnie. All rights reserved. 26 Chalder Street, Newtown, NSW, 2042, Australia. CompuServe : 100033,2346 UseNet: amcb@runx.oz.au Information in this document is subject to change without notice, and is not guaranteed to be a complete description of the clX program. CONTENTS What is clX? 1 Using clX 5 The clX Main Menu. 5 Using Menu Items 1 and 2. 5 Viewing the clX Report. 6 Printing the clX Report. 7 clX Main Menu: Other Menu Items. 7 Check-list of clX menu items that MUST be set up. 9 Saving the clX Option Settings. 9 Explanation of the clX Report. 11 clX Style Options 13 Specify Annexure Banner. 13 Specify Definition Section Number. 14 Specify Type of Quote Marks. 14 Specify Maximum Clause Number. 15 Specify Clause Format Used. 16 clX Processing Options 19 19 Ignore single character definitions. 19 Ignore Uncapitalised Definitions. 20 Set Ignore Character Option 1 & 2. 20 clX Reporting Options 21 Produce Observations and Errors Only. 21 Produce a verbose report. 21 Set report page width. 21 Set report page length. 22 Set printer control sequences. 22 Error Reporting Options 23 Syntactic Issues 25 25 Identification of Clause Numbers. 25 Assembly of Clause Numbers. 25 Processing of Clause Number References. 26 26 Processing of Document Attachments or Annexures. 26 clX Error Messages 27 Software Signature Check. 27 Observation and Errors Report. 28 Copyright 1992, Andrew McBurnie Abnormal Termination Messages. 29 Technical Appendix 32 Installation Notes. 32 Operational Notes. 32 Processing Notes. 34 INDEX page 43 Copyright 1992, Andrew McBurnie Chapter 1 What is clX? The Clause Cross Referencer, or "clX", will help you in the drafting, negotiation and redrafting of any document which contains numbered paragraphs and internal references. clX will analyse your document, identifying clause or paragraph numbers, and listing references in the text to these paragraphs. The program will also attempt to identify such serious errors as references to clause numbers that do not exist. A sample fragment from a typical report is set out below. Clause '16.2.' has 9 references: 7.9.e.iv. 7.9.e.v 16.3 16.3.f (2) 16.3.f.iv 16.4. 16.5. 16.6. In the above fragment, you are given a list of clause numbers which contain references to clause 16.2. Note that the representation of clause numbers is 'normalised' so that dots are always used as subclause separators, replacing parentheses wherever they are used. Clause 16.3(f) has two references. clX will identify paragraph numbers whether you have used automatic paragraph numbering, or whether you have manually entered your paragraph numbers. All that is required is that you have specified the character numbering format, or template, to clX using the menu options available. In many drafting styles, clauses are not labelled with complete clause numbers. For example, a clause labelled only as "(c)", might be part of clause 6.2, and therefore its full number is 6.2(c). Even though lower level paragraph numbers do not carry the full clause number, such as one like 6.2(c), clX will assemble the full clause number for cross reference purposes. The Clause Cross Referencer will expand clause number references so that all the clauses within the range are identified as referents. For example, if a phrase such as "clauses 7.3 through 7.9" occurs in some clause 3.1, then 3.1 will be listed as a reference against 7.3, 7.4, 7.5, 7.6, 7.7, 7.8 and 7.9. The clX program actually tries to follow the text of your document, using natural language processing technology. Some techniques used by clX are more akin to the way humans read text Copyright 1992, Andrew McBurnie 2 clX description than the usual way computer process text, in that "rules of thumb", or "heuristic" methods are employed to extract the required information. This is because natural language is never completely consistent, and judgement is required to interpret it. (Because of ambiguities and irregularities in the English language, and the range of drafting styles which may be used by authors, the extraction of relevant data by clX is not guaranteed to be either complete, or accurate.) You control the way clX processes your documents by using a "control panel", a system of menu screen displays which appear when you start the program. Using the control panel, you can specify to clX relevant details of your drafting style, for example, your method of clause numbering. You can prevent clause sequence error messages from appearing. In summary, The Clause Cross Referencer is able to help you in the contract drafting, negotiation and redrafting process in the following ways: 1. by identifying clauses or definitions that contain references to non-existent clauses; 2. by picking out apparent clause sequence errors, or omitted clauses; 3. by allowing you to quickly locate references to a particular clause which you wish to change. Administrative Matters. You may use clX for a free 30 day trial period. During that period, you are strongly advised to carefully evaluate its capabilities against your particular drafting style. If you continue to use clX after the 30 day trial period, you are required to obtain a license. The licence fee is based on $US 125 per user, with volume discounts. Licence details and fees may be found in the accompanying file, "CLXREGIS.TXT". The contents of that file are also reproduced at the end of this manual. The licensor of clX is Generic Software Pty Ltd (ACN 054 834 196), a proprietary company registered in Australia. Send discettes containing problem documents to the address given at the front of this manual. Copyright 1992, Andrew McBurnie clX description 3 For Lawyers: For lawyers, a new program called, "cX, the Contract Cross Referencer", is now available. cX offers all the facilities of clX, plus the ability to cross reference contract definitions, and also to cross reference contract annexures or attachments. It produces three cross reference reports: one for definitions, one for clauses and one for annexures/attachments. cX is not distributed as shareware. It is available for a license fee based on $US220 per user, from the address given at the front of this manual. Refer to the file "CXADVERT.TXT" for further information and volume discount information. clX users may upgrade to cX by paying the difference between the clX price and the cX price, for the appropriate number of users. Copyright 1992, Andrew McBurnie 4 clX description Copyright 1992, Andrew McBurnie Chapter Two Using clX Introduction. This chapter tells you what you need to know to be able to run clX under normal circumstances, with no special settings. The following chapters explain further clX options which may be used to control reporting and cross referencing. Your systems administrator will have installed the clX software for you according to your local installation standards. Technical instructions about the installation of clX are in the "Technical Appendix" section at the end of this manual. The clX Main Menu. To begin a session with clX, simply type the command, 'CLX', and tap the 'return' or 'enter' key. Following display of the clX logo, copyright and licensing information, (during which various set up procedures occur), the main clX menu will be displayed: 1. Specify document for cross referencing 2. Start Cross Referencing 3. Set Drafting Style Options 4. Set Processing Options 5. Set Reporting Options 6. Set Error Detection Options _____________________________________________ Press 'Esc' or 'q' to QUIT clX, or select one of the above options by typing its number: Using Menu Items 1 and 2. Items 1 and 2 on this menu are the ones you will use most often. On selecting item 1, the clX main menu will be replaced with a message requesting you to type in the name of the document to be Copyright 1992, Andrew McBurnie 6 Using clX processed - that is, the PC DOS name under which the document is stored. If the document to be processed is not in the current directory, you must type in a full PC DOS path name. clX will first check that the document specified can be found, and will then give you the name of the listing file into which the cross reference report will be written. This file will have the same name as the one you entered, but with the suffix ".LST". If you specified a document in another directory, (that is, you typed a path name something like, for example, "\banking\overseas\binvest.doc"), then the report file will be placed back in that directory. If you do not agree with proposed name (and directory location) for the report file, you may edit the output report name yourself. clX will give a warning message if the name of the report file which you enter conflicts with an existing file. clX won't let you enter a report file name which is the same as the document you specified for cross referencing. After you have specified the name of the file to be processed, the main menu will appear again. You will now see the document name that you entered displayed against menu item 2. For example if you specified the document name, "binvest.doc", then menu item 2 will read, 'Start Cross Referencing binvest.doc'. If you change your mind at this point, and wish to specify a different document for processing, simply select menu item 1 again. Otherwise you can now select menu item 2, "Start Cross Referencing ...", for processing to begin. If you select menu item 2 without having entered the name of a document for processing, an error message will appear. While cross referencing is proceeding, the menu will be replaced by a display showing the current reference and referent being processed, and the amount of memory remaining. If, while cross referencing is proceeding, you decide that you wish to halt processing, you should be able to accomplish this by simultaneously pressing the 'control' and 'c' keys, or the 'control' and 'break' keys. On many keyboards, the 'control' key is labelled, "Ctrl". Viewing the clX Report. Copyright 1992, Andrew McBurnie Using clX 7 When cross referencing is completed, the "REPORT VIEWING" menu will appear, shown below. If you select item 1 on this menu, the clX report will be displayed on the screen for you to browse. 1. Browse Report 2. Print Report _____________________________________________ Press 'Esc' or 'q' to QUIT clX, or select one of the above options by typing its number: For browsing, use the Page Down, Page Up and up/down arrow keys to scroll through the clX report listing. The 'Home' key will always take you to the top of the report. The 'End' key will cause the report to be scrolled rapidly forward; just tap any key to halt it. This is just a way of moving quickly through the report. As with the menus, the 'Esc' or 'q' key will return you from the clX browser to the clX menu system. The clX browser contains its own help screen. This help screen will appear any time you tap a key that the browser does not recognise. Printing the clX Report. The "REPORT VIEWING" Menu item 2 will print the clX cross reference report. Your systems administrator will have arranged for the report to be directed to the appropriate printer. clX Main Menu: Other Menu Items. The remaining items on the menu are used to set up the normal way clX is to be used in your organisation, by specifying elements of your drafting style, and the way in which clX is to process and report upon your documents. You may also wish to make temporary changes to your normal clX setup. For example, you may want to temporarily change the reporting options to produce only an errors and observations report. Subsequent chapters explain these menu items in more detail. Copyright 1992, Andrew McBurnie 8 Using clX Copyright 1992, Andrew McBurnie Using clX 9 Check-list of clX menu items that MUST be set up. The following parameters, from the Drafting Style Options menu, must be set to values appropriate to your documents before clX will produce useful results. Annexure Banner. Type of Quote Marks. Maximum Clause Number. Clause Format used. (absolutely vital) For explanations of all the above, refer to the details of the "Style Options" menu in Chapter 4. Also, if your documents have special markup characters such as asterisks or hash signs, refer in Chapter 5 to the explanation of two available set up options which instruct clX to ignore certain characters in your documents. Your mark ups may prevent clX correctly identifying some clause numbers. This sometimes happens with unspecialised precedent documents, or template documents. (However, a basic assumption behind clX is that it is to be used to process 'normal' documents, not precedent, or template text, which may have contain all kinds of strange formats and characters, and numbered annotations or instructions which will also look like clause numbers.) Saving the clX Option Settings. The options you set up for controlling clX are only saved when you actually process a document, that is, select the clX main menu option number 2, 'Start Cross Referencing'. Thereafter, they will appear as the default settings every time you start up clX. If, however, you change some clX options and then quit clX without actually performing a cross reference, your option settings will not be saved, and will revert to the original settings the next time you start up clX. Special Notes. clX makes use of a special parameter file which will appear in your work area, or directory. This file is called "clx$$$$$.pam", and should not be deleted. It contains the options needed to run clX according to your requirements. Copyright 1992, Andrew McBurnie 10 Using clX One of the areas controlled by the clx$$$$$.pam file is the format of the clauses used in your documents. Because clX does not assume any defaults in this area, specification of a clause format is a required item. If a clause format has not been set up, clX will decline to begin cross referencing. You need to select item 5 on the Style Options menu to be able to proceed. This topic is covered in more detail in chapter four. Copyright 1992, Andrew McBurnie Chapter Three Explanation of the clX Report. Introduction. This chapter explains the report produced by clX. First, a word of caution. We are certain that clX is a valuable tool that will perform the essentially low level clerical exercise of cross referencing more quickly, efficiently and accurately than a human being can. But the English language is a baroque medium, and drafting styles are incredibly varied. It is therefore likely that there will always be syntactical forms which clX has not come across. You should not assume that the report will always contain all the references and errors that exist in a document. (License purchasers receive 12 months support, during which omissions may be able to be fixed.) Ultimately, the clX report complements your own expertise and knowledge of your text; it do not replace it. The clX Report. A clX report contains two sections: - an Observations and Errors section. This contains notes on apparent clause sequence errors and references to non-existent targets. - A Clauses Cross Reference. For each clause and all its subclauses, all other clauses and definitions which can be identified as referring to that clause are listed. Each item in a cross reference section starts with the clause number being cross referenced, followed by all the references. (Refer to the example in Chapter 1.) Any reference to "clause 0" in the report actually refers to anything that occurs before clause 1. This means material right at the start of the document - for contracts, the list of parties, recitals and so on. For those drafting legal documents, note that if you number the parties to an agreement at the beginning of a document, or number the statements under a "Recitals" or "Whereas" heading, clX will treat these numbered items as clause numbers if they match the clause format you have selected for processing. This may cause Copyright 1992, Andrew McBurnie 12 The clX Report some confusion with the 'identical' clause numbers that appear later. If you see the name of a definition in a list of references, instead of a clause number, this means that a clause number reference is to be found in the body of the definition text. If you had subsidiary clause numbers in the text of the definition, these will be appended to the definition title appearing in your clX report, appearing following a '#' mark. This will serve to more accurately locate references in the text of a lengthy definition. A number in parentheses after a reference is a count of the number of times a reference occurred. A number following an '@' sign on a reference means that the reference occurs in the indicated attachment, or annexure. Refer back to the Observations and Errors section, and you will see a message indicating the particular contract attachment, or annexure, which clX has assigned to the number that follows the '@' symbol. The phrase '[no clause]' used in a reference means that the reference occurred at a location where there was no current clause number. This often happens in annexures, and will therefore usually be associated with an '@' indicator. References to clause 0, mentioned above, are a special case of '[no clause]'. An asterisk, '*', in front of a reference signals that the reference occurred in the definition section of a contract, but there was no current definition text. The definition section number is usually substituted. This sometimes happens in attachments to a contract, when a clause number is used which happens to be the same clause number as is used for the definitions section in the main document. The following are examples of the more complicated references which could occur: 5.1@2 (4) -- Four references by clause 5.1 in annexure 2. *[no clause]@2 (3) - There are three references in annexure 2, they should have been in a definition, but weren't, and there wasn't a clause number either ... which all means that annexure 2 contains text but only one clause number. Copyright 1992, Andrew McBurnie Chapter Four clX Style Options Introduction. This chapter explains how to specify elements of your drafting style for clX. The menu described is reached via item 3 of the clX main menu. On selection of the Style Options menu, the following menu will appear: 1. Specify Annexure Banner(s). 2. Specify Definition Section Number. 3. Specify Type of Quote marks. 4. Specify Maximum Clause Number. 5. Specify Clause format used. ______________________________________________ Press 'Esc' or 'q' to return to the Main Menu, or select one of the above options by typing its number: On the Style Options menu as actually displayed, the current settings for each option will be displayed against each line. These will either be options which you have chosen, or defaults which were saved from the previous cross referencing session. Specify Annexure Banner. On selecting this item, a menu will be displayed which allows you to enter the names of up to two types of contract annexure or attachment, eg, "Schedule", "Exhibit", "Annexure" are examples of attachments headings which you might need to specify here. An annexure or attachments banner is used to specify the name you apply to attachments or annexures in the document to be processed. For example, if your attachments are headed, "SCHEDULE A", "SCHEDULE B", and so on, then the name you should enter for this option would be 'SCHEDULE'. This is the 'attachment banner' in this instance. clX looks for attachments like "SCHEDULE A" immediately at the start of a new paragraph - whether it is centred or not does not matter. Upper or lower case banners will be accepted. If you have attachments/annexures at the end of a document, and clX does not detect them, perhaps due to an incorrect banner specification, any clause number references they contain will still be identified and cross referenced. However, this information will not be distinguished from that of the body of the document. For example, a reference, say, to clause 4.3 which Copyright 1992, Andrew McBurnie 14 clX Style Options appears in clause 1 of an attachment will just be reported as a reference by clause 1, not "clause 1@2". Note that if you use a layout style for annexure headings that spaces out the letters, then clX will be unable to pick them out. For example, a heading like "A N N E X U R E" will not be correctly identified. Only "ANNEXURE" will be seen by clX. Specify Definition Section Number. This item is probably only applicable if you are drafting a legal contract. On selecting this item, a message will be displayed asking you to type in a particular clause number. Use this item to specify the clause number of the section that contains your interpretive provisions, or definitions. What you enter here should be a number which is the top level of your clause formatting sequence. For example, in 2.1(a)(iii), the top level number is '2'. You should not type in '2.1', or '2.1(a)', etc. The main use of this entry is to allow clX to produce a more helpful cross reference report. References found inside a section nominated as the definitions section will cause clX to use the title of the current definition as the reference, instead of the current clause number. This is quite important, because if your definitions section is large, and you have many references in the text of your definitions, you will be able to pin-point them much more easily if the definition title is used by clX than just the clause number of the definition section, (typically clause 1). Specify Type of Quote Marks. On selecting this item, a message will be displayed asking you to choose the type of quote marks you normally use to delineate definition titles. That is, double quotes -"- or single quotes - ` and '. If you process a document in which the quote marks do not match the type specified by this option, then definitions will not be identified. If you do not delimit the titles of your definitions in quote marks, but bold or italicise them, then, for Word Perfect users only, a special version of clX can be supplied on request. However, be warned, it will not perform nearly as well in picking Copyright 1992, Andrew McBurnie clX Style Options 15 out definitions. This is because w/p users sometimes mark text for bolding or other character attributes in strange ways, eg, the words "Force Majeur", might actually be: [BOLD]Force M[bold][BOLD]ajeur[bold][BOLD[bold]. clX is just not clever enough to handle all possibilities in this area, though it will try. Specify Maximum Clause Number. On selecting this item, a message will be displayed asking you to type in a particular clause number. Once Clause numbers which are higher than the clause number you specify here are found, clX will regard this as the end of the document. Clause numbers higher than the maximum clause number will not be recognised, and contract attachments will be ignored. Again, what you enter for this option should be a number from the top level of your clause formatting sequence. For example, in 30.1(a)(iii), the top level number is '30'. A number, that is digits, should always be entered for this option. In order for a maximum clause number to have the effect of terminating a clX pass, there must be no sequence errors. In particular, a maximum clause number, if detected, will only halt processing if it is one greater than the immediately previous clause number. You may use the maximum clause number option to restrict clX processing to the early part of a document. However, there is another use which clX makes of the maximum clause number option. This second use of the maximum clause number option is as a simple way of preventing clX from mistaking some types of number as clauses, a common example being street numbers. The number you enter for this option should therefore be the highest clause number likely to be used by most of your documents. However, it is important that the number is realistic, and not set too high. As suggested above, you may need to change this option from document to document in some circumstances. The maximum clause number concept refers only to the principal document, not to attachments. If you have a table of contents at the front of your document, the maximum clause number option could cause clX to terminate Copyright 1992, Andrew McBurnie 16 clX Style Options while reading the contents table, on the entry that corresponds to the maximum clause number. Normally, however, clX should detect content tables. Specify Clause Format Used. On selecting this item, a list of different clause format options will be displayed, from which a choice should be made. You should choose the clause formatting option, or template, corresponding to the drafting style that you require. The menu options appear as follows: A. 1.1(a)(i)(A)(I) B. 1.1.1.1.1.1 C. 1(a)(i)(A)(I) D. A.1.1(a)(1)(A) E. 1.1(a)(1)(A) F. 1A.(1)(a1)(i) The menu items are labelled 'A' through to 'F' for selection. The 'pseudo clauses' which appear against 'A' through 'F' in the list of menu items are patterns, or templates, which describe in a precise manner a particular clause number formatting style. Each letter or number indicates the type of a particular sub- clause, as follows: 1 - a sequence of Arabic digits, ie 0 to 9. a - a sequence of lower case letters, ie a to z. A - a sequence of upper case letters, ie A to Z. i - a sequence of lower case Roman numerals. I - a sequence of upper case Roman numerals. The symbols used to separate a subclause appear in the patterns. For example in "1.1", the dot indicates that clX will look for an actual dot to separate the two subclauses. In "1.1(a) ... ", the left and right parentheses are the symbols which clX will use to separate the next subclauses, and so on. For example, in format option 'A', which is "1.1(a)(i)(A)(I)", clX will recognise clause numbers such as: 23.2, 11.16(a), 5.4(c)(i), and so on. Further, clX will recognise individual subclauses when they appear on separate paragraphs, and put them together to assemble the full clause number for cross referencing purposes. If you do not see your particular clause format in the options displayed above, please contact the author. Normally, your usual clause format would be a saved option, and you will not have to use this menu item. However, should you Copyright 1992, Andrew McBurnie clX Style Options 17 change it to process a particular document, perhaps one from another organisation which has a different drafting style, you should remember to change it back again for your normal documents. The selection of a clause format option that does not match that of the document being processed may cause clX to generate many spurious error messages. If you accidentally specify a clause format that does not match the clause formatting actually used, clX may detect this, and will halt in the early stages of processing to ask if you wish to continue. The analysis clX does to decide whether an incorrect clause format may have been selected is an intelligent guess. There is a possibility that clX may not detect that the wrong format has been selected, or may halt with this query even though you have not made an error. Note that documents that contain more than one method of clause formatting will cause clX to produce incomplete and/or odd results. Copyright 1992, Andrew McBurnie 18 clX Style Options Copyright 1992, Andrew McBurnie Chapter Five clX Processing Options Introduction. This chapter explains how to prevent clX from becoming confused by markup characters, primarily those that are likely to appear directly against clause numbers, and also to fine tune the manner in which definitions are used in contracts. The menu described is reached via item 4 of the clX main menu. On selection of the Processing Options menu, the following menu will appear: 1. Ignore single character definitions. 2. Ignore uncapitalised definitions. 3. Set Ignore Character Option 1. 4. Set Ignore Character Option 2. ______________________________________________ Press 'Esc' or 'q' to return to the Main Menu, or select one of the above options by typing its number: On the Processing Options menu that you actually see displayed, the current settings for each option will be displayed against each line. These will either be options you have chosen, or defaults that were saved from the previous cross referencing session. Ignore single character definitions. This feature allows you to fine tune the references which appear in the clX report for maximum relevance. Sometimes you may find that 'definitions' such as "A", "B" or "X" and "Y" are being picked up by clX. A single character enclosed in quotes may often be meaningless and should not be taken as definition title. They typically result from explanations of terms in formula. For example: (X - Y) / X "X" means ... "Y" means ... These may well not be true definitions, defined globally for the entire document, but 'local' definitions, which may appear more than once in different types of formula scattered throughout the document. The 'scope' of their meaning is confined to that of a single clause or definition. Copyright 1992, Andrew McBurnie 20 clX Processing Options The 'Ignore single character...' menu option allows you to stop the appearance of such entries. The default setting for this option is Yes. Ignore Uncapitalised Definitions. This feature allows you to fine tune the references which appear in your clX report for maximum relevance. The text of a definition titled, "The System" could happen to contain minor quoted material which should not itself be treated as a definition title. Its acceptance by clX would result in any references between it and the next definition title being ascribed to it, and not to "The System". This feature has been added for those drafting legal contracts. Set Ignore Character Option 1 & 2. Occasionally, some documents contain special characters that prevent the correct identification of clause numbers and other important syntactic components, if concatenated with them. These options give you the chance to tell clX to by-pass up to two particular characters before syntactic analysis. If you specify, for example, that the character # is to be ignored, the effect is as if you had used a word processing program to delete all occurrences of # from the document, prior to running it through clX, (although clX does not alter a document it reads). You should make use of this feature if you have used special markup characters against clause numbers, since otherwise clX will be unable to identify them. NOTE : you should not 'ignore' characters which are used as delimiters in clause numbers, eg, ., (, ). The default settings for these options are "[" and "*". Copyright 1992, Andrew McBurnie clX Processing Options 21 Chapter Six clX Reporting Options Introduction. This chapter explains how to control the way clX produces reports. The menu described is reached via item 5 of the clX main menu. Item 5, Report Options. On selection of item 5 of the main menu, the following menu will appear: 1. Produce Observations and Errors only. 2. Produce a verbose report. 3. Set report page width. 4. Set report page length. 5. Set printer control sequences. ______________________________________________ Press 'Esc' or 'q' to return to the Main Menu, or select one of the above options by typing its number: As it actually appears on the screen, the above menu will also show the current settings for each item. Produce Observations and Errors Only. This option allows you to prevent clX printing the clause cross reference. Cross referencing still happens, but only the Observations and Errors report is produced. Produce a verbose report. This option should normally be left set as NO. If selected, it will produce a lengthy Observations and Errors report, listing every clause and definition found in the document. You may very occasionally need to use this option to see more clearly how clX has interpreted a document. Set report page width. Select this option to specify the page width in characters for the clX report. Copyright 1992, Andrew McBurnie Set report page length. Select this option to specify in lines the page length of the clX report. Set printer control sequences. This option is used to control the way in which your clX reports are printed. It will normally have been set for you by your systems administrator. The option prompts to enter two lines of up to eighty characters of special text. The first will be sent to your printer to put it into an appropriate mode for printing your clX report, and the second to set it back to your normal mode. One common use of this facility would be to set your printer to use non-proportional text, to prevent distortion of the columnar clX report layout. Refer to the Technical Appendix of this manual for more detailed instructions on the use of printer control sequences. This option is intended for technical support personnel. Copyright 1992, Andrew McBurnie clX Reporting Options 23 Chapter Seven Error Reporting Options Introduction. This chapter explains how to prevent clX reporting clause number sequence errors. The menu described is reached via menu item 5 of the clX main menu. Item 5, Error Reporting Options. On selection, this option will display the following: Report clause sequence problems? [Y/N] : Report Clause sequence errors: Currently YES Normally this option is set to "YES". Respond "N" if you do not wish clause sequence errors to be reported. Copyright 1992, Andrew McBurnie Copyright 1992, Andrew McBurnie Chapter Eight Syntactic Issues Introduction. The purpose of this chapter is to outline some major processing techniques used by clX, and to indicate some clX processing limitations. Processing of Definitions. clX identifies a definition name anywhere in a document if it is enclosed in quotes, and is also associated with certain syntactic structures that match the internal rule base of clX. Identification of Clause Numbers. At the end of every paragraph in a document, clX will examine the first few characters of the next paragraph to decide if a clause number is present. Any sequence of characters immediately following the end of a paragraph which, according to the template supplied by the clX control panel, is syntactically a valid clause number, will be accepted as a clause number unless certain other adjacent syntactic structures suggest that it is not. This means that there is a possibility that some things that are not clause numbers, but happen to occur at the beginning of a paragraph, could be identified by clX as a clause number. clX will be able to distinguish most of these cases correctly. clX is unable to distinguish numbered lists of things from clauses. Eg, in the phrase, "... shall be the aggregate of (i) , (ii) ." the roman numerals are just being used to enumerate a list of things, not to number some clauses. (This is regarded as a somewhat intractable problem.) Assembly of Clause Numbers. If you make use of Roman numerals in your drafting style, note that the paragraph numbering sequence: ' ... (h) ... (i)' can be ambiguous. clX may interpret the '(i)' as an alphabetic 'i', not the Roman numeral 'one'. If it happens at all, this should only happen in references, not paragraph numbers. Copyright 1992, Andrew McBurnie 26 Syntactic Issues Similar comments apply to the clause number sequences, ' ... (k) ... (l)' and '... (u) ... (v)' This could result in some erroneous non-existent clause reference messages. Processing of Clause Number References. Multiple letter subclause numbers: Multiple letters in subclause numbers, such as (aa), (ab), are supported, but may generate erroneous clause sequence number error messages. Roman Numerals: Only roman numerals up to 99 are supported in clause number references. A limitation on the Detection of Clause Reference Errors: Although clX can normally detect references to non-existent clauses, it cannot detect references to incorrect clauses. That is, clX is unable to see that a reference to a clause that actually exists is really a reference to the wrong clause - ie, the reference does not make any logical sense. Processing of Document Attachments or Annexures. In clX, the presence of an attachment is tested for immediately following the end of a paragraph, just as is the presence of a new clause number. If an attachment is to be recognised, it must have a banner which matches the option selected from the clX menu system. (For example, in "Schedule B", the banner is the word, 'Schedule'.) The attachment name itself, that is the title that follows the attachment banner, is expected to be a single word. Any attachments found will be displayed in a comment message in the Observations and Errors Report, assigning to each a reference number to be used in the cross reference report. For example, references contained in ANNEXURE "A", will appear with '@1' against them. Copyright 1992, Andrew McBurnie Chapter Nine clX Error Messages Introduction. The purpose of this chapter is to explain the meaning of selected messages, whose origin may lie in an operational issue or semi- technical problem. This chapter does not contain a complete list of all the clX messages. If error messages are produced that do not appear to be correct, registered users may send details to the Author, attaching a copy of the document which clX has apparently failed to process, for a period of twelve months from the date of license payment receipt. All documents must be supplied on diskette, not just in printed form. The English language is infinite, and computers are finite devices. There is no guarantee that the problem can be fixed, but reasonable efforts will be made to address the problem. Many of the messages described below have several different forms. The descriptions show these variants in a particular notation which uses text enclosed in angle brackets, for example, , and text enclosed in braces, for example { | }. Something like should be read to mean that in the actual message which appears on the clX report, the < ... > will be replaced by a real clause number. Something like, { | }, means that two alternatives may actually appear in the message. In this example, there may be either a or a , but not both. The | symbol separates the alternatives. Software Signature Check. On opening a w/p document for processing, clX first checks that the w/p software manufacturer's signature information in the header matches the type of document for which it is configured to process. Warning notes may appear at the beginning of the Observations and Errors report if the version number is wrong. For the 2.2 Word Perfect version of clX, these messages are: "*** Warning, specified file contains an internal code which indicates that one of Word Perfect's other products has created it - it may not be a w/p file." "*** Warning, specified file was not created by Word Perfect, version 5.1 or 5.2" Copyright 1992, Andrew McBurnie 28 clX Error Messages If the correct signature information cannot be found at all, then clX will decline to process the document, and return to the main menu to display the following message: "Not a Word Perfect version 5.'n' document" or "Not a recognised MS Word document" Observation and Errors Report. This section explains the main error messages which may appear in the Observations and Errors report: " *** ERROR: { | } contains a reference to a non-existent clause - ." This message warns you that a reference appears to have been made to a clause number in the text of the document, but the clause number cannot be found in the document. If this message appears, but you think it is wrong, refer to the section headed 'Processing of Clause Number References' in the Chapter on "Syntactic Issues", where you may find some indication of the reasons for its appearance. This non-existent clause number message may be followed by the qualifying statement, "( *** Above may be a reference to a clause in another document.") " *** ERROR: { | } contains a reference to a non-existent clause at the top of a range - " This is the same type of error as described previously. The only difference is that it has been found in a phrase such as, "... clauses 3.6 through 3.9...", and means that clause 3.9 could not be found. "{ | } *** lower and upper clause references are equal - , ." Copyright 1992, Andrew McBurnie clX Error Messages 29 This error message warns you that in a phrase such as, "... clauses 3.6 through 3.6 ..." the low clause and the high clause are the same. "{ | } *** upper clause of range is less than lower - , " This error message warns you that in a phrase such as, "... clauses 3.6(c) through 3.6(a) ...", the high clause is less than the low clause. "*** Invalid clause reference at "{ | }" This error message warns you that a clause reference in the body of your text did not match the clause format template which you specified using the Style Options menu. "**** Pass 2, RefLst is full - " " *** - is too long" The number of characters being assembled into a clause number was so many that an internal storage array was insufficient, and processing of the clause was abandoned. "**** CRASH - too may subclauses in a list of references at clause " This error message occurs when an internal limit within clX is exceeded. It means that a list of subclause references was being processed, eg, something like, "clauses (a), (b), (c) ... etc" and that there were too many subclauses in this list. Currently, this internal limit is set to fifty. Abnormal Termination Messages. The following messages appear only when something has gone badly wrong inside the clX program. " *** ... came to default case in parser" Copyright 1992, Andrew McBurnie 30 clX Error Messages Refer the above message to the Author. "clXfinishStatus() called with null message" Refer this message to the Author. "can't find control panel" clX was unable to open the clx$$$$$.pam" file. Refer this message to your systems administrator. "unexpected EOF while looking for parameter banner" "unexpected EOF while reading clause format specifier" "unexpected EOF while reading QuoteType" "unexpected EOF while reading switch" "invalid clause format specifier" "level too high in clause format specifier" "invalid subclause type specifier" "invalid RNULLAllowed switch" "invalid definition section specifier" "invalid Quote Type specifier" All the above mean either that the clx$$$$$.pam file has become corrupted, or that clX itself has been incorrectly configured. "No input file specified" "No output file specified" "Output file has same name as input" "can't create clX listing file" "too many parameters" "clX control panel load failed" "**failed to write control panel!**" "** can't find clXback executable **" "clX config problem... rule base image lost" "rulebase ... clX internal config problem" "clX rulebase image ..." " -- can't find clXfront executable" All the above will be caused by some configuration problem with clX, or just possibly running out of disk space. Copyright 1992, Andrew McBurnie clX Error Messages 31 "no driver" "no " "no graphics" Any of the above may suggest some hardware problem with the workstation, or that clX has been incorrectly configured for you. "avlTree - not enough memory" "dynMem - not enough memory" "dList - not enough memory" "Ran out of memory" A very large and complex document could cause clX to run out of memory. If this happens on a large document, you could request your systems administrator to configure a special PC without your usual TSR's, network drivers, etc, to save space in conventional memory. If using DOS version 5, make sure you take full advantage of the "load High" capabilities. Finally, the following termination messages could appear if severe internal processing problems occur. They are part of the original debugging code for clX, and have been left enabled. "stack overflow!" "dList - attempted to linkout from an empty list" "dList - attempted to get from empty list" "dList - attempted update of empty list" "avlTree - insert called with nullpointer" "avlTree - duplicate key during insert" The possibility of any of these abnormal termination messages occurring is remote. Copyright 1992, Andrew McBurnie Technical Appendix Installing clX; Operational Notes Introduction. This appendix is intended to be used by a systems administrator. It provides technical information about the installation and running of clX. Installation Notes. The Clause Cross Referencer consists of four separate executable files, or .EXE files, which must all be copied on to your system. The executable files are clx.exe, clxovl1.exe, clxovl2.exe and clxovl3.exe. In addition the following text files should be present: clxman.txt (this manual), clxregis.txt (important instructions on how to pay the author), clxintro.txt, and readme.txt, clxplans.txt, clxupd.txt. The clX program is not copy protected. If yours is a large computer installation, you will already have your own standards for the location of software. The only requirement for clX is that all the executable files must be in the same directory, or on the same executable path. If you are installing clX on one or more stand-alone machines, the most convenient method of installation may be to create a directory called "CLX", and copy the contents of the clX files into it. The name of the directory which you have created for clX must then be added to the 'path' command in the 'autoexec.bat' file of the root directory. There are no special set up options required at the time of installation. The only task for installation is to copy the clX executable files on to your system, and also the "clx$$$$$.pam" file, which should also be present. Operational Notes. The operation of the clX program is controlled by a parameter file called "clx$$$$$.pam", which clX assumes is always located in the current path. This clx$$$$$.pam file contains code sequences which specify such things as the format used for clause sequencing, page dimensions for the clX report, what type of errors are to be detected, and other items. These sequences are generated by the clX menu system under the control of the user. Copyright 1992, Andrew McBurnie Technical Appendix 33 New control parameters set up by the user are only written out to the clx$$$$$.pam file when the user selects a document for cross referencing, and begins cross reference processing. If a clx$$$$$.pam file is not present in the current directory when clX is started, then one will be created based on standard internal default settings, and the user will be invited to change them. In particular, the user must select a clause format style, as clX has no internal defaults in this area. During normal operation, clX will create a work file in the current directory called "clx$$ret.pam". This will always be deleted by clX itself, and should not normally be seen. The size of this file will never be larger than about fifty characters. The cross reference report is written to a listing file in the current path of the same name as the input file, with the suffix ".LST", or as nominated by the user. Following production of a listing file, clX will optionally print it to the standard DOS PRN: device, or you can print the file separately using the DOS print command. The listing file will contain ordinary ascii text, with no control characters other than LF-CR sequences and form feed characters, unless as described in the next paragraph. Printers which are set up for proportional fonts may distort the columnar layout of the reports. Item 5 on the Report Options menu will allow you to set up hexadecimal control sequences appropriate to your printer. You can set up a starting sequence and a reset sequence which will bracket the text of the clX report. You must enter each hex character in a printer control sequence as two ascii characters from the set 0-9, A-F, representing each of the four bits. The two character pairs forming each control sequence must be contiguous. You have the 'usual' keyboard based editing facilities for creating hex control strings. For moving the cursor: left and right arrow keys, the home and end keys. The insert key will toggle insert mode of and off. Delete characters using backspace and delete. Delete to the end of a string with Control+End. Delete to the start of a string with Control+Home. The 'Enter' or 'Return' key will signify the end of the control sequence. So will an up or down arrow. Copyright 1992, Andrew McBurnie 34 Technical Appendix Processing Notes. Processing by clX is in two phases: a first pass which collects all the clauses, and a second pass which reads the document again to collect clause references. The program seeks to the beginning of the document to begin the second pass; it does not close and reopen the document. The second pass is slower than the first. clX builds its cross reference tables in memory dynamically, and will therefore utilise as much conventional memory below 640K as is available and is required. clX does not use expanded or extended memory. The presence of terminate and stay resident programs, device drivers, and other software such as a network operating system shell, will all contribute towards reducing the memory available to clX. Note that it is possible that some DOS memory management programs may interfere with the operation of clX. For example QEMM 386 from Quarterdeck may do this on a networked system. Ensure that utilities such as QEMM are configured not to control areas of memory in the first megabyte which are used by network adaptor cards or you may find that clX experiences problems, for example claiming that a document is not a Word Perfect 5 document, and refusing to process it. Copyright 1992, Andrew McBurnie page 35 clX 2.2, The Clause Cross Referencer ("clX"). (Word Perfect version) Registration/Licensing (PC DOS version) You may use clX for a 30 day trial period, provided you abide by the terms of the license agreement. (During the trial period, you are strongly advised to carefully evaluate the Software's capabilities against your particular drafting style.) If you continue to use clX after the 30 day trial period, you are obligated to purchase a license. Recipients of clX must be informed, in advance, that any fee paid to acquire clX from a distributor does not relieve recipients of their obligation to purchase a license from the licensor if they use clX. The PC DOS files which constitute clX, must be distributed together, including all associated text files (.TXT). clX may only be bundled with other products with written permission from the Licensor. Upon payment of the licence fee, you will receive an up to date copy of clX, future updates as they appear, and 12 months support. Please complete the following and read the attached Terms and Conditions. Completion of and signing this form constitutes an agreement to take the Software named above on License subject to the Terms and Conditions below. LICENSEE INFORMATION Licensee Name: ......................................... Licensee Contact: ......................................... License Telephone: ........................... Licensee Address: Street ........................................... Suburb ........................................... City ........................................... Postcode/Zip ............ E-Mail Address(es): ...................................... Where did you obtain your copy of clX ? .................................. Disk size: 5.25" / 3.5" (cross out one). clX LICENCE FEE: $US 125.00 for one user. (or equivalent amount in other currencies) clX, Licensing Agreement. Technical Appendix page 36 Refer to the scale below for volume pricing information. Number of Users: ..... Total Price: ...... (use scale below) Copyright 1992, Andrew McBurnie clX, Licensing Agreement. page 37 clX Registration, Word Perfect Version. Schedule of Fees -oOo- Note: Prices are in US dollars. No License Users Fee ===== ======= 1 $125 2 $234 3 $338 4 $436 5 $530 6 $618 7 $701 8 $780 9 $855 10 $925 11 $991 12 $1,053 13 $1,110 14 $1,164 15 $1,213 16 $1,259 17 $1,301 18 $1,339 19 $1,373 20 $1,403 21 $1,430 22 $1,453 23 $1,473 24 $1,489 25+ $1,500 The price for 25 or more users is $US 1,500. Copyright 1992, Andrew McBurnie clX, Licensing Agreement. Technical Appendix page 38 LICENSEE AGREEMENT ================== I have read, understood and agree to all the Terms and Conditions of this License Agreement as attached: Licensee Signature ......................................... Name and Title ......................................... Date ......................................... LICENSE FEES (The license fee is as indicated in the schedule of fees above) NUMBER OF USERS : ......... TOTAL LICENSE FEE : $US......... (Read off price against number of users in the Schedule above.) NOTE: Make cheques payable to : "Generic Software Pty Ltd". Send cheques and signed agreement to : Generic Software Pty Ltd, 26 Chalder Street, Newtown, NSW, 2042, AUSTRALIA. TERMS and CONDITIONS ==================== THIS LICENCE AGREEMENT IS ENTERED INTO BETWEEN GENERIC SOFTWARE PTY LTD, ACN 054 834 196, A COMPANY REGISTERED IN AUSTRALIA, (HEREIN REFERRED TO AS "LICENSOR") OF THE ONE PART AND YOU, THE LICENSEE, ON THE OTHER. PLEASE READ THIS DOCUMENT CAREFULLY BEFORE USING THE LICENSOR SOFTWARE THE SUBJECT OF THIS LICENSE. BY USING THE SOFTWARE, INCLUDING FOR TRIAL PURPOSES, YOU AGREE TO BECOME BOUND BY THE TERMS OF THIS AGREEMENT, WHICH INCLUDES THE SOFTWARE LICENSE AND DISCLAIMER OF WARRANTY. Copyright 1992, Andrew McBurnie clX, Licensing Agreement. page 39 THIS DOCUMENT CONSTITUTES A LICENSE TO USE THE SOFTWARE ON THE TERMS AND CONDITIONS APPEARING BELOW. The computer program referred to as "clX, The Clause Cross Referencer, (Word Perfect version)", and related documentation and materials (herein collectively referred to as "the Software") are licensed, not sold, to you for use only upon the terms of this license, and Licensor reserves all rights not expressly granted to you. 1. License. (a) This License allows the Software to be used by up to the number of users in your organisation indicated at "NUMBER OF USERS", above. (b) If at any time you wish to have more users of the software than indicated at "NUMBER OF USERS", you must pay Licensor an additional amount for the additional numbers of users, this additional amount being the difference between the cost for the number of current users and the cost for the new number of users as set under "clX Registration, Schedule of Fees". (c) No monies are refundable by Licensor if you choose to decrease the number of users. (d) You are granted a limited license to distribute copies of the Software for the trial use of others subject to the conditions described below. (i) The PC DOS files, clx.exe, clxovl1.exe, clxovl2.exe, clxovl3.exe, clxman.txt, clxintro.txt, clxregis.txt, clxupd.txt, clxplans.txt and readme.txt, which constitute the Software, must be distributed together. (ii) You may charge a nominal fee for distribution of the Software. The recipient of the Software must be informed, in advance, that any such nominal fee paid to acquire the Software does not relieve the recipient of their obligation to purchase a license for the Software if the recipient uses the Software. (iii) the Software may only be bundled with other products with written permission from Licensor. Copyright 1992, Andrew McBurnie clX, Licensing Agreement. Technical Appendix page 40 (f) You may also copy the Software for distribution to the number of licensed users in your organisation, if that is necessary, and also for the purposes of backup. 2. Restrictions. (a) YOU MAY NOT MODIFY, ADAPT, TRANSLATE, OR CREATE DERIVATIVE WORKS BASED UPON THE SOFTWARE OR ANY PART THEREOF. (b) The Software contains trade secrets and to protect them you may not decompile, reverse engineer, disassemble or otherwise transform the Software to a humanly perceivable form. You agree not to divulge, directly or indirectly, any such trade secrets to any person. 3. Termination. This License is effective until terminated. The License will terminate automatically without notice from Licensor if you fail to comply with any provision of this License. Upon termination of this license for any reason: (a) you shall have no right to refund of the whole or any part of the license fees or other amounts paid for this license and the Software licensed hereunder (except in the circumstances and expressly as provided in Section 5 below); and (b) you shall continue to be bound by the provisions of Section 2 above. Termination shall be without prejudice to any rights Licensor may have as a result of breach of this Agreement. 4. Limited Warranty. (a) Licensor warrants the media in which the software is recorded and supplied to you as free from defects in materials and faulty workmanship under normal use for a period of ninety (90) days from the date of delivery. During this warranty period, Licensor will, at its option, repair or replace, free of charge, defective media upon which the software has been supplied (and if necessary restore the Software thereon). (b) For twelve months from the date of license fee receipt, Licensor will examine copies of documents supplied in Word Perfect 5.1 or 5.2 format from Licensee, which Copyright 1992, Andrew McBurnie clX, Licensing Agreement. page 41 Licensee asserts is processed incorrectly by the software. Licensor will make reasonable efforts to identify the cause of the problem, and supply a new version of clX if this is practicable. Licensor may decide, and has sole discretion to decide, that no resolution of the problem is possible, and such decision by Licensor will be final. (c) LICENSEE UNDERSTANDS AND AGREES THAT BECAUSE OF AMBIGUITIES AND IRREGULARITIES IN THE ENGLISH LANGUAGE, AND IN THE RANGE OF DRAFTING STYLES WHICH MAY BE USED BY AUTHORS, THE EXTRACTION OF ALL RELEVANT DATA BY THE SOFTWARE IS NOT GUARANTEED TO BE EITHER COMPLETE OR ACCURATE. 5. Disclaimer of Warranty, Limitation of Remedies. TO THE FULL EXTENT PERMITTED BY LAW, LICENSOR HEREBY EXCLUDES ALL CONDITIONS AND WARRANTIES, WHETHER IMPOSED BY STATUTE OR BY OPERATION OF LAW OR OTHERWISE, NOT EXPRESSLY SET OUT HEREIN. THE SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND EXCEPT AS PROVIDED IN SECTION 4 ABOVE. LICENSOR DOES NOT WARRANT, GUARANTEE OR MAKE ANY REPRESENTATIONS REGARDING THE USE, OR THE RESULTS OF THE USE, OF THE SOFTWARE WITH RESPECT TO ITS CORRECTNESS, ACCURACY, RELIABILITY, CURRENTNESS OR OTHERWISE. THE ENTIRE RISK AS TO THE RESULTS AND PERFORMANCE OF THE SOFTWARE IS ASSUMED BY YOU. EXCEPT AS SPECIFICALLY SET FORTH IN THIS SECTION 5, LICENSOR MAKES NO EXPRESS OR IMPLIED WARRANTIES OR CONDITIONS INCLUDING, WITHOUT LIMITATION, THE WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE SOFTWARE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY LICENSOR, ITS DEALERS, DISTRIBUTORS, AGENTS OR EMPLOYEES SHALL CREATE A WARRANTY OR IN ANY WAY INCREASE THE SCOPE OF THIS WARRANTY, AND YOU MAY NOT RELY ON ANY SUCH INFORMATION OR ADVICE. IMPORTANT NOTE: Nothing in this Agreement is intended or shall be construed as excluding or modifying any statutory rights, warranties or conditions which are applicable to this Agreement or the Software supplied hereunder, and which by virtue of any national or state Fair trading, Trade Practices or other consumer legislation may not be modified or excluded. If permitted by such legislation, however, Licensor's liability for any breach of any such warranty or condition shall be and is hereby limited to either: Copyright 1992, Andrew McBurnie clX, Licensing Agreement. Technical Appendix page 42 (a) the supply of such part of the Software licensed hereunder again; or (b) the correction of any defect in any such part of the Software licensed hereunder as Licensor at its sole discretion may determine to be necessary to correct the said breach. EXCEPT AS SET OUT IN THIS SECTION 5, IN NO EVENT SHALL LICENSOR BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, AND LOSS OF BUSINESS INFORMATION OR COMPUTER PROGRAMS), EVEN IF LICENSOR OR ANY LICENSOR REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Except as expressly set out in this section 5, Licensor's maximum liability for damages arising under this Agreement shall be limited to the license fees paid by you for that part of the Software supplied by Licensor hereunder which caused the damages or that is the subject matter of, or is directly related to, the cause of the action. 6. General. This Agreement will be construed under the laws of the state of New South Wales. This Agreement contains the entire Agreement between the parties hereto with respect to the subject matter hereof, and supersedes all prior agreements and/or understandings (oral or written). Failure or delay by Licensor in enforcing any right or provision hereof shall not be deemed a waiver of such provision or right with respect to the instant or any subsequent breach. If any provision of this Agreement shall be held by a court or competent jurisdiction to be contrary to law, that provision will be enforced to the maximum extent permissible, and the remaining provisions of this Agreement will remain in full force and effect. Copyright 1992, Andrew McBurnie page 43 INDEX Annexures/attachments processing of 26 specifying string of characters for clX to recognise 13 browse 7 clX report 7 browser 7 clause format 9-11, 13, 16, 17, 29, 30, 33, 10, 16, 17 Clause number ambiguity in identification 25 Identification of 25 specify format 16 specify maximum 15 spurious error messages if wrong format specified 17 spurious errors messages if multiple formats used 17 subclause numbers 25, 26 unable to distinguish from numbered lists 25 Clause number references 1 limitation on error detection 26 clause numbering 2 clauses cross reference 11 control panel 2, 25, 30, 2, 32 parameter file 9 cross reference 1, 3, 6, 7, 9, 11, 14, 21, 26, 33, 34 Cross reference report 11, 33 Defaults settings 9 Definitions primary identifying features 25 quoted references not recognised 25 Specify Definition section number 14 directory 6, 9, 32, 33 Document attachments attachments 13 drafting 1, 2, 5, 7, 9, 11, 13, 14, 16, 17, 20, 25, page 35, page 41 drafting style 2, 5, 7, 9, 13, 16, 17, 25, page 35, 2 Help screen 7 Interpretive provisions 14 main menu 5-7, 9, 13, 19, 21, 23, 28, 5, 9 Markup characters Ignoring 20 maximum clause number 9, 13, 15, 16, 15 memory 6, 31, 34 Menu item items which must be set up 9 natural language 1, 2 Natural language processing technology 1 Copyright 1992, Andrew McBurnie page 44 Observations and Errors 11, 12, 21, 26-28, 11 Producing only 21 Observations and Errors Report attachments noted 26 Original settings 9 Page dimensions Report 21, 22 parameter 9, 30, 32 parameters 9, 30, 33 path name 6 PC DOS 6, page 35, page 39 precedent documents 9 printer 7, 21, 22, 33 printing 7, 21, 22 QEMM 34 Quote Marks Specify type of 14 Report 7 Report page layout, possible distortion of 33 Reports 11 Systems administrator 5, 7, 22, 30-32, 5, 7, 32 Copyright 1992, Andrew McBurnie